- El Hospital Universitario Ramón y Cajal mejora la gestión integral de medicamentos gracias a la tecnología
- NCSC Publishes Tips to Tackle Malvertising Threat
- Indra se alza con el contrato para la modernización del sistema de comunicaciones tierra-aire de Estados Unidos
- The best AI search engines of 2024: Google, Perplexity, and more
- ChatGPT has officially replaced Google Search for me - here's why
Verifying the Platform State of the Cisco PGW 2200 Softswitches
Verifying the Platform State of the Cisco PGW 2200 Softswitches
You can determine which of your Cisco PGW 2200 Softswitches is the active Cisco PGW 2200 Softswitch and which is the standby Cisco PGW 2200 Softswitch. If your system uses a Cisco PGW 2200 Softswitch in a simplex configuration, the single Cisco PGW 2200 Softswitch is always active. To do this, complete the following steps:
Step 1 Log into one of the Cisco PGW 2200 Softswitches, start an MML session, and enter the following command to determine its platform state:
rtrv-ne
The system should return a message, similar to the following, if it is currently the active Cisco PGW 2200 Softswitch:
MGC-01 – Media Gateway Controller 2008-10-07 02:56:16.623 EDT
M RTRV
“Type:MGC”
“Hardware platform:sun4u sparc SUNW,Sun-Fire-V210”
“Vendor:”Cisco Systems, Inc.””
“Location:MGC-01 – Media Gateway Controller”
“Version:”9.8(1)””
“Platform State:ACTIVE”
The valid values for the Platform State field are ACTIVE, STANDBY, or OOS.
Step 2 Log into the other Cisco PGW 2200 Softswitch, start an MML session, and enter the following command to determine its platform state:
rtrv-ne
The system should return a message that indicates that it is in either the active or standby platform state.
If the Cisco PGW 2200 Softswitches have changed their platform state, determine why the switchover occurred by searching the contents of the active system log file, as described in the “Viewing System Logs” section on page 8-83.
Under normal operations, one Cisco PGW 2200 Softswitch should be active and the other Cisco PGW 2200 Softswitch should be standby.
If the platform state of either Cisco PGW 2200 Softswitch is OOS, check the alarms as described in the “Monitoring the Alarms Status” section, and take the actions necessary to correct the condition that caused the associated alarm(s). The alarms that require you to take corrective action and their associated actions can be found in the “Alarm Troubleshooting Procedures” section on page 8-4. A complete listing of alarms can be found in the Cisco PGW 2200 Softswitch Release 9 Messages Reference.
If the platform state of both Cisco PGW 2200 Softswitch is active, proceed to Step 5.
Step 3 Use the following command to quit the MML session:
quit
Step 4 Verify that the active configuration has not changed using the following UNIX commands:
cd /opt/CiscoMGC/etc
ls -l
The system returns a response similar to the following:
total 35350
-rw-r–r– 1 mgcusr mgcgrp 38240 May 8 10:46 02.trigger
-rw-rw-r– 1 mgcusr mgcgrp 20488 Oct 10 2000 64eisup.bat
lrwxrwxrwx 1 mgcusr mgcgrp 43 Aug 1 18:55 active_link ->
/opt/CiscoMGC/etc/CONFIG_LIB/CFG_pol-addipl
-rw-rw-rw- 1 mgcusr mgcgrp 30907 Jul 24 15:29 alarmCats.dat
-rw-rw-rw- 1 mgcusr mgcgrp 2064 Jun 4 10:57 alarmTable.dat
-rw-rw-rw- 1 mgcusr mgcgrp 0 Jun 4 10:57 auxSigPath.dat
Identify the active_link file. The listing indicates which configuration is currently active. The active configuration in the example is CFG_pol-addipl.
If the configuration has changed, you may want to compare the active configuration to the previous configuration.
Step 5 Collect system data as described in the “Collecting System Data for Cisco TAC” section on page 8-87 and contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request” section on page xx.
Verifying That Processes Are Running
To verify that the processes on your Cisco PGW 2200 Softswitch are running, perform the following steps:
Step 1 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the following command:
rtrv-softw:all
The system returns a response similar to the following:
Note This is an example on Cisco PGW 2200 Softswitch Release 9.7(3) Patch 14. The system output varies based on your software version, patch version, and configuration.
MGC-01 – Media Gateway Controller 2008-04-16 00:22:02.696 EDT
M RTRV
“CFM-01:RUNNING ACTIVE”
“ALM-01:RUNNING ACTIVE”
“MM-01:RUNNING ACTIVE”
“AMDMPR-01:RUNNING ACTIVE”
“CDRDMPR-01:RUNNING ACTIVE”
“DSKM-01:RUNNING IN N/A STATE”
“MMDB-01:RUNNING IN N/A STATE”
“POM-01:RUNNING ACTIVE”
“MEASAGT:RUNNING ACTIVE”
“OPERSAGT:RUNNING ACTIVE”
“Replic-01:RUNNING ACTIVE”
“ENG-01:RUNNING ACTIVE”
“IOCM-01:RUNNING ACTIVE”
“TCAP-01:RUNNING IN N/A STATE”
“FOD-01:RUNNING IN N/A STATE”
“LMAGT-01:RUNNING ACTIVE”
“pril3-1:RUNNING IN N/A STATE”
“mgcp-1:RUNNING IN N/A STATE”
<Press ‘SPACE’ for next page, ‘Enter’ for next line or ‘q’ to quit this output>
“h248-1:RUNNING IN N/A STATE”
“sip-1:RUNNING IN N/A STATE”
“eisup-1:RUNNING IN N/A STATE”
“eisup-2:RUNNING IN N/A STATE”
“ss7-i-1:RUNNING IN N/A STATE”
“m3ua-1:RUNNING IN N/A STATE”
“sua-1:RUNNING IN N/A STATE”
“iua-1:RUNNING IN N/A STATE”
Note If any of the processes are stopped, you can see “process name:STOPPED” in the system output.
Note If this MML command is entered on the standby Cisco PGW 2200 Softswitch, the state of the processes is either RUNNING STANDBY or RUNNING IN N/A STATE.
Step 2 If any of the processes are initializing, wait a few moments and repeat Step 1. If that process is still initializing, contact the Cisco TAC for assistance. See the “Obtaining Documentation and Submitting a Service Request” section on page xx for more information on contacting the Cisco TAC.
If any of the processes are stopped, contact the Cisco TAC for assistance. See the “Obtaining Documentation and Submitting a Service Request” section on page xx for more information on contacting the Cisco TAC.
